Analytics enabled radio access network (RAN)- aware content optimization using mobile edge computing

ABSTRACT

A central analytics server can be utilized to analyze health data associated with one or more radio access networks (RANs) that has been aggregated from one or more mobile edge computing (MEC) servers, to determine throughput available at a radio link interface associated with a user equipment (UE). Further, the central analytics server can determine, based on the available throughput, a recommendation for an action that can be performed by a content server to optimize content delivery to the UE. In an example, the central analytics server can convey the recommendation to the content server(s) via a “window size” field within a header segment of a transmission control protocol (TCP) via in-band and/or out-of-band signaling. In one aspect, the recommendation can comprise instructions to adapt a bit stream and/or comprise instructions indicative of an optimal data transmission route.

TECHNICAL FIELD

The subject disclosure relates to wireless communications, e.g., asystem and method for analytics enabled radio access network (RAN)-awarevideo optimization using mobile edge computing.

BACKGROUND

The rapid growth in mobile communication has resulted in an exponentialincrease in traffic within mobile networks that has created severalchallenges for mobile network operators (MNOs). Additionally, newhigh-demand services and applications have emerged due to the evolutionof user equipments (UEs). To conserve UE resources, these high-demandservices and applications can be offloaded to a conventional centralizedcloud (CC). However, this option can cause a significant executiondelay, which is substantially increased in congested networks and isunsuitable for real-time applications.

To prevent delays, mobile edge computing (MEC) can be utilized, whereincomputation and storage resources provided at an edge (e.g., radioaccess network (RAN)) of the mobile network, can be utilized to executethe high-demand services and applications while satisfying strictlatency criteria. The MEC can employ content caching and/or contextawareness mechanisms to improve the service providing ability of theRAN. Moreover, the MEC environment is characterized by ultra-low latencyand high bandwidth as well as real-time access to radio networkinformation that can be leveraged by the applications. MNOs can provideauthorized third-parties access to their RAN edge allowing them toflexibly and rapidly deploy innovative applications and services towardsmobile subscribers, enterprises, and vertical segments.

The above-described background relating to mobility networks is merelyintended to provide a contextual overview of some current issues and isnot intended to be exhaustive. Other contextual information may becomefurther apparent upon review of the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system that facilitates analytics enabledradio access network (RAN)-aware content optimization.

FIG. 2 illustrates an example system for controlling, via in-bandsignaling, content delivery parameters that have been determined basedon RAN analytics.

FIG. 3 illustrates an example system for controlling, via out-of-bandsignaling, content delivery parameters that have been determined basedon RAN analytics.

FIG. 4 illustrates an example system comprising a central analyticsserver that provides, to content servers, guidance data that can beutilized to optimize a transmission of a content delivery service.

FIG. 5 illustrates an example system that facilitates automating one ormore features in accordance with the subject embodiments.

FIG. 6 illustrates an example method that facilitates adjustment of adata transmission from a content server based on throughput availabilitythat is conveyed to the content server via in-band and/or out-of-bandsignaling.

FIG. 7 illustrates an example method for determining alternate routesfor content delivery, according to an aspect of the subject disclosure.

FIG. 8 illustrates an example system that depicts a service-based 5Gnetwork architecture operable to execute the disclosed embodiments.

FIG. 9 illustrates an example system that depicts a non-roaming 5Gsystem architecture in reference point representation that is operableto execute the disclosed embodiments.

FIG. 10 illustrates a block diagram of a computer operable to executethe disclosed communication architecture.

FIG. 11 illustrates a schematic block diagram of a computing environmentin accordance with the subject specification.

DETAILED DESCRIPTION

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It may be evident,however, that the various embodiments can be practiced without thesespecific details, e.g., without applying to any particular networkedenvironment or standard. In other instances, well-known structures anddevices are shown in block diagram form in order to facilitatedescribing the embodiments in additional detail.

As used in this application, the terms “component,” “module,” “system,”“interface,” “node,” “platform,” “server,” “controller,” “entity,”“element,” “gateway,” “point,” or the like are generally intended torefer to a computer-related entity, either hardware, a combination ofhardware and software, software, or software in execution or an entityrelated to an operational machine with one or more specificfunctionalities. For example, a component may be, but is not limited tobeing, a process running on a processor, a processor, an object, anexecutable, a thread of execution, computer-executable instruction(s), aprogram, and/or a computer. By way of illustration, both an applicationrunning on a controller and the controller can be a component. One ormore components may reside within a process and/or thread of executionand a component may be localized on one computer and/or distributedbetween two or more computers. As another example, an interface cancomprise input/output (I/O) components as well as associated processor,application, and/or API components.

Further, the various embodiments can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement one or moreaspects of the disclosed subject matter. An article of manufacture canencompass a computer program accessible from any computer-readabledevice or computer-readable storage/communications media. For example,computer readable storage media can comprise but are not limited tomagnetic storage devices (e.g., hard disk, floppy disk, magnetic strips. . . ), optical disks (e.g., compact disk (CD), digital versatile disk(DVD) . . . ), smart cards, and flash memory devices (e.g., card, stick,key drive . . . ). Of course, those skilled in the art will recognizemany modifications can be made to this configuration without departingfrom the scope or spirit of the various embodiments.

In addition, the word “example” or “exemplary” is used herein to meanserving as an example, instance, or illustration. Any aspect or designdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Rather, use ofthe word exemplary is intended to present concepts in a concretefashion. As used in this application, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or.” That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform.

Moreover, terms like “user equipment,” “communication device,” “mobiledevice,” “mobile station,” and similar terminology, refer to a wired orwireless communication-capable device utilized by a subscriber or userof a wired or wireless communication service to receive or convey data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream. The foregoing terms are utilized interchangeably inthe subject specification and related drawings. Data and signalingstreams can be packetized or frame-based flows. Further, the terms“user,” “subscriber,” “consumer,” “customer,” and the like are employedinterchangeably throughout the subject specification, unless contextwarrants particular distinction(s) among the terms. It should be notedthat such terms can refer to human entities or automated componentssupported through artificial intelligence (e.g., a capacity to makeinference based on complex mathematical formalisms), which can providesimulated vision, sound recognition and so forth.

Further, it is noted that the term “cloud” as used herein can refer to aset of servers, communicatively and/or operatively coupled to eachother, that host a set of applications utilized for servicing userrequests. In general, the cloud computing resources can communicate withuser devices via most any wired and/or wireless communication network toprovide access to services that are based in the cloud and not storedlocally (e.g., on the user device). A typical cloud computingenvironment can include multiple layers, aggregated together, thatinteract with each other to provide resources for end-users.

Aspects or features of the disclosed subject matter can be exploited insubstantially any wired or wireless communication technology; e.g.,Universal Mobile Telecommunications System (UMTS), Wi-Fi, WorldwideInteroperability for Microwave Access (WiMAX), General Packet RadioService (GPRS), Enhanced GPRS, Third Generation Partnership Project(3GPP) Long Term Evolution (LTE), Third Generation Partnership Project 2(3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA),Fifth generation (5G) and/or other future telecommunicationtechnologies, Zigbee, or another IEEE 802.XX technology, low power widearea (LPWA) and/or non-3GPP standard based solutions, such as, but notlimited to, Ingenu, Sigfox, and/or LoRa, etc. Additionally,substantially one or more aspects of the disclosed subject matter can beexploited in legacy (e.g., wireline) telecommunication technologies.

As the development of mobile communication continues to rapidlyincrease, wireless data traffic has observed an explosive growth. Inaddition, the demand for applications and/or services that havehigh-capacity and/or low-latency requirements has also increased. Tomeet the high-capacity and/or low-latency requirements, MNO can deploymobile edge computing (MEC; also referred to as multi-access edgecomputing) to provide cloud computing capabilities and an IT serviceenvironment at the edge of a communication network (e.g., cellularnetwork). The European Telecommunications Standards Institute (ETSI)specifies that MEC can be a part of the eNodeB (eNB) or can be run on anexternal server that is deployed between the eNB and the mobile corenetwork on an S1 interface. However, the conventional MEC lacks QoSand/or disaster recovery mechanisms.

In one or more embodiments, systems and methods disclosed herein providea central analytics server (e.g., operations support systems (OSS)server) that has a global view of the communication network and itsinterfaces. The central analytics server can analyze health dataassociated with one or more radio access networks (RANs) that has beenreceived from one or more MEC servers, to determine throughput availableat a radio link interface. Further, the central analytics server candetermine, based on the available throughput, a recommendation for anaction that can be performed by a content server to optimize contentdelivery. In an example, the central analytics server can convey therecommendation to the content server(s) via a receive window field(e.g., utilized for flow control) within a segment of a transmissioncontrol protocol (TCP) header via in-band and/or out-of-band signaling.In one aspect, the recommendation can comprise instructions to adapt abit stream and/or comprise instructions indicative of an optimal (and/orpreferred) content delivery route.

Referring initially to FIG. 1, there illustrated is an example system100 that facilitates analytics enabled RAN-aware content optimization,according to one or more aspects of the disclosed subject matter. System100 can be utilized within a communication network (e.g., cellularnetwork) that facilitates MEC, wherein computing, storage and/orcommunication resources, deployed at a network edge, can providedetailed analytics data on the network, the customer premises equipment(CPE), and/or the user equipment (UE). In one aspect, MEC servers 102can be deployed at the edge of a mobile network, for example, coupled to(and/or be part of) an access point, RAN controller, etc. and can beutilized to provide new services by opening the RAN edge. As an example,the MEC servers 102 can run virtualized software on commercialoff-the-shelf (COTS) hardware housed within a secure form factor. Withthe proliferation of new wireless technologies and next generationmobile devices, connectivity and communication models can be expected torapidly evolve and drive the adoption of new services which were notpossible before. Moreover, as network functions transform from aphysical to a virtual domain (e.g., in a cloud centric environment),innovative opportunities can be created to be able to design fullyprogrammable mobile networks, for example, network that can deliver amicro-service architecture. Programmable or adaptive network technologyconcepts can be applied to core networks and can be extended to radioaccess networks.

In an aspect, the MEC servers 102 can be deployed across one or moredifferent (or the same) types of RANs (e.g., HetNets) that utilizedifferent (or the same) radio access technologies (RATs). Typically, theMEC servers 102 can facilitate content caching and/or execution ofservices and/or applications of authorized service providers to providean ultra-low latency, high bandwidth, and/or real-time access to radionetwork information. Further, MEC servers 102 can be utilized to monitordata associated with various network elements, such as, but not limitedto, user equipment (UE), RAN devices, radio interface, etc.

According to an embodiment, a RAN analytics component 104 can beutilized to determine (and/or predict via machine learning) informationassociated with the RAN, such as, but not limited to, RAN health dataand/or status, current loading of a cell and/or neighboring cells, adirection of UE movement through the cell, a predicted movement of a UEto the cell edge, information and/or status of UE (e.g., type andmodel/make of device, battery status, screen size, memory available,caching, traffic pattern, applications/service utilized etc.). Further,the RAN analytics component 104 can determine statistics pertaining toquality of service (QoS), quality of experience (QoE), bandwidthavailability and/or utilization, capacity, and/or throughput at a radiodownlink interface for a UE. As an example, the RAN analytics component104 can monitor and/or collect information at most any time, such as,but not limited to, periodically, at a defined time, in response to anevent, based on instructions received from an OSS server 106, etc.

According to an aspect, the OSS server 106 can comprise a centralanalytics server, for example, deployed within a core network cloud ofthe cellular network, that can receive and analyze the information fromthe RAN analytics component 104 (from one or more of the MEC servers102). As an example, the information can be transmitted via a 16-bitreceive window field of a transmission control protocol (TCP) headerthat is typically utilized for flow control data. Moreover, theinformation can be transmitted via in-band and/or out-of-band (e.g.,Satellite) communication and can accordingly support disaster recoverylogic.

Based on an analysis of the received information, the OSS server 106 candetermine an action that can be performed by one or more content servers108 to optimize delivery of content (e.g., to satisfy defined criteriaassociated with QoS, QoE, etc.). For example, OSS server 106 candetermine adjustments that can be made to a transmission of the contentto maintain defined quality parameters. Additionally, alternatively, theOSS server 106 can determine one or more alternate distribution pathsfor content delivery. In one aspect, the OSS server 106 can transmit therecommendations to the content server via the 16-bit receive windowfield of the TCP header that is typically utilized for flow controldata. Moreover, the recommendations can be transmitted via in-bandand/or out-of-band (e.g., satellite) communication and can thus supportdisaster recovery logic.

The content server(s) 108 can perform the recommended actions based theinformation conveyed in the TCP header. For example, the contentserver(s) 108 can adjust the data transmission to the UE to maintain thequality in-band or out-of-band (e.g., satellite) communication. Inanother example, the content server(s) 108 can utilize an alternatetransmission route to facilitate content delivery and accordinglyconform to the service level agreement (SLA).

MEC can complement software-defined networking (SDN) and networkfunction virtualization (NFV) to facilitate the evolution to nextgeneration networks (e.g., 5G networks) that can be highly resourceintensive in terms of handling mobile-to-mobile, Internet of things(IoT), augmented/virtual reality (AR/VR), tele-health, targeted mobileadvertising, connected cars, and/or other new services/technologies.These new services/technologies can require a wide range of aggregatebit rates, low latencies, device types and/or device capabilities,device densities, etc., to provide consistent end user quality for agiven service in a heterogeneous networking environment. Moreover,utilization of the system 100 can help satisfy the demandingrequirements for these services/technologies (e.g., content deliveryservices) with regards to expected throughput, latency, scalability,and/or automation.

Referring now to FIG. 2, there illustrated is an example system 200 forcontrolling, via in-band signaling, content delivery parameters thathave been determined based on RAN analytics, in accordance with anaspect of the subject disclosure. In one aspect, the system 200 utilizesMEC server 202 deployed within an edge cloud 204 that providescloud-computing capabilities and an IT service environment at the edgeof a cellular network. Deploying the MEC server 202 within the edgecloud 204 enables the MNO to provide, through edge analytics, a bettercustomer experience by enabling services that have lower latency, higherthroughput, and/or are more diverse, localized, and/or personalized. Itis noted that the MEC server 202 can be substantially similar to MECservers 102 and can comprise functionality as more fully describedherein, for example, as described above with regard to MEC servers 102.

According to an aspect, the MEC server 202 can determine and/or estimate(e.g., by employing RAN analytics component 104) a bandwidth and/orthroughput available and/or likely to be available at a radio downlinkinterface for UE 206 that is served by access point 208 (e.g., eNB,HomeNodeB, gNB, base station, etc.). As an example, the MEC server 202can perform measurements with respect to most any RAN performanceparameters, such as, but not limited to, bandwidth, throughput,capacity, load, packet loss, out of sequence, delay/latency, health of alink, etc. Moreover, the measurements can be performed periodically, inresponse to an event, based on a request/instruction from the OSS server106, etc. Further, in this example embodiment, the measured data can betransmitted to the OSS server 106 via in-band signaling (e.g., within a16-bit receive window field of a TCP header that is used for flow forcontrol).

According to an embodiment, the OSS server 106 can analyze the measureddata to identify optimal data transmission parameter(s) and/or route(s)for content delivery (e.g., streaming video, audio, etc.). Moreover, theOSS server 106 is deployed centrally within a core cloud 210 and thus,has a global view of the network and its interfaces, connectionavailability, and/or alternate route availability. Further, the OSSserver 106 can determine current and/or future (e.g., predicted)bandwidth availability view by leveraging a built-in analyticsfunctionality that can be utilized to perform trending analysis to havefuture rules for the available bandwidth predictability. Based on thedetermined bandwidth availability and/or other performance parametersassociated with the RAN, the OSS server 106 can determine optimal datarouting path that can be utilized to facilitate content delivery. In oneaspect, the OSS server 106 can store a table of all the alternatedistribution paths, comprising, but not limited to, wireless, cable,powerline and/or satellite communication channels that can be utilizedto deliver content from content server 108 to the UE 206 and based onthe determined bandwidth and/or other performance parameters of thepaths, the OSS server 106 can select one (or more) of the distributionpaths for routing the content to the UE 206.

As an example, the OSS server 106 can communicate the determinedinformation (e.g., bandwidth availability and/or alternate distributionroute(s)) to the content server 108 via in-band signaling (e.g., withina 16-bit receive window field of a TCP header that is used for flow forcontrol). The content server 108 can utilize the information to adaptthe byte stream to satisfy QoS and/or SLA. According to an aspect, theinformation transmitted to the content server 108 conveys the RAN'soverall health (e.g., available capacity, available bandwidth, etc.)determined based on observed and/or forecasted traffic demand. RANhealth can be determined (e.g., by the OSS server 106) in many ways,such as, but not limited to utilizing the statistics of a specificgeographical area (e.g., based on a zip code) and/or specific radio headusing customer analytics. Moreover, the OSS server 106 can utilize thenetwork RAN analytics in conjunction with customer device analytics todetermine the the overall RAN health, specifically, the throughputavailable at the radio link interface and based on the overall RANhealth, recommend, to the content server 108, a suitable course ofaction to efficiently deliver content to the UE 206. Accordingly, thecontent server 108 does not need to implement its own routing ordisaster recovery functionalities. Moreover, the OSS server 106 can actas a central intelligence node for a one stop solution for bandwidthdetection and/or alternate distribution path.

The content server 108 can receive the recommendations and be aware ofthe available bandwidth and/or can continue the content delivery serviceto the UE 206 by using different data distribution path (e.g., based onthe recommendation from the OSS server 106), should be it needed (e.g.,bandwidth available on current path is below a defined threshold). It isnoted that the UE 206 can comprise, but is not limited to most anyindustrial automation device and/or consumer electronic devices, forexample, a tablet computer, a digital media player, a wearable device, adigital camera, a media player, a cellular phone, a personal computer, apersonal digital assistant (PDA), a smart phone, a laptop, a gamingsystem, set top boxes, home security systems, an IoT device, a connectedvehicle, at least partially automated vehicle (e.g., drones), etc.

Referring now to FIG. 3, there illustrated is an example system 300 forcontrolling, via out-of-band signaling, content delivery parameters thathave been determined based on RAN analytics, in accordance with anaspect of the subject disclosure. It is noted that the OSS server 106,content server 108, MEC server 202, edge cloud 204, UE 206, access point208, and core cloud 210 can comprise functionality as more fullydescribed herein, for example, as described above with regard to systems100-200. In this example embodiment, the OSS server 106 can communicatewith the MEC server 202 and/or the content server 108 via out-of-bandsignaling, for example, using satellite links via satellite 302. As anexample, the measurement data, transmitted from the MEC server 202 tothe OSS server 106, can be included within a 16-bit receive window fieldof a TCP header that is used for flow for control. Further, therecommendation data, transmitted from the OSS server 106 to the contentserver 108, can be included within a 16-bit window size field of a TCPheader that is used for flow for control. As an example, the window sizefield is reserved for indicating a maximum amount of received data, inbytes, that can be buffered at one time on the receiving side of aconnection.

In one aspect, the MEC server 202 can transfer the RAN analytics datadirectly to the content server 108 via out-of-band signaling (e.g.,using satellite links via satellite 302) under the control of the OSSserver 106. As an example, the RAN analytics data can be included withina 16-bit window size field of a TCP header that is used for flow forcontrol. Although FIG. 3 depicts an embodiment wherein the OSS server106 communicates with the MEC server 202 and the content server 108 viasatellite signals, it can be appreciated that the subject disclosure isnot so limited and that in some embodiments the OSS server 106 cancommunicate with the MEC server 202 via in-band signaling whilecommunicating with the content server 108 via out-of-band signaling, orcommunicate with the MEC server 202 via out-of-band signaling whilecommunicating with the content server 108 via in-band signaling.

Referring now to FIG. 4, there illustrated is an example system 400 thatcomprises a central analytics server (e.g., OSS server 106) thatprovides, to content servers, guidance data that can be utilized toimprove and/or optimize a transmission of a content delivery service,according to an aspect of the subject disclosure. It is noted that theOSS server 106 can comprise functionality as more fully describedherein, for example, as described above with regard to systems 100-300.

In one aspect, a data collection component 402 can be utilized toreceive measurement data determined by one or more MEC servers (e.g.,MEC servers 102) associated with one or more RANs. As an example, thedata collection component 402 can receive the measurement data in a pushand/or pull configuration, periodically, during a defined time interval,in response to an event (e.g., a request for content deliverytransmitted by a UE, initiation and/or establishment of a contentdelivery session, etc.), etc. In one aspect, the data collectioncomponent 402 can request the MEC servers to track specific parameters.Typically, the measurement data can include most any information relatedto RAN health, QoS, bandwidth utilization and/or availability, capacity,throughput, etc. at the radio downlink interface for a UE. According toan embodiment, the data collection component 402 can receive themeasurement data via in-band and/or out-of-band (e.g., satellite links)communication (e.g., to support disaster recovery). As an example, a TCPheader segment's 16-bit window size field (e.g., that is typicallyutilized to provide a size of the receive window) can comprise themeasurement data.

An analysis component 404 can be utilized to aggregate the received dataand evaluate the aggregated data to determine if any changes are to bemade to optimize a content delivery session, for example, to ensure QoSand/or QoE criteria is met. As an example, the optimization cancomprise, but is not limited to, adapting data transmission parametersfor the content delivery session (e.g., media rate selection,video/audio rate adaptation, transcoding, etc.), determining an optimalstart time for initiating the content delivery and/or an optimal timeperiod during which the content is to be delivered (e.g., based ondetermining that bandwidth availability estimated at the optimal starttime/time period satisfies a defined bandwidth criterion), selecting anoptimal format for the content, etc. As an example, the analysiscomponent 404 can determine the changes based on various factors, suchas, but not limited to, RAN health, connection availability, bandwidthavailability/usage, capacity availability and/or RAN load, UE analytics,type of content, etc.

In one embodiment, a route determination component 406 can be utilizedto determine an optimal path for routing the content delivery sessionfrom the content server to the UE. As an example, the routedetermination component 406 can verify if the determined bandwidth(and/or other RAN parameters) satisfy a low bandwidth criterion (e.g.,determine is the available bandwidth is less than a defined thresholdassociated with the QoS/QoE). If the determined bandwidth does notsatisfy the low bandwidth criterion (e.g., the available bandwidth isgreater than or equal to the defined threshold), the route determinationcomponent 406 can recommend that the current and/or defaultcommunication path be utilized for content delivery. Alternatively, ifthe determined bandwidth satisfies the low bandwidth criterion (e.g.,the available bandwidth is less than the defined threshold), the routedetermination component 406 can recommend that an alternatecommunication path (e.g., via satellite links, powerline links, cablelinks, etc.) be utilized for content delivery. Since the OSS server 106has a global view of the network and its interfaces and/or availability,the OSS server 106 can store information (e.g., availability, bandwidth,capacity, etc.) associated with one or more alternate communicationpaths, including wireless, cable, powerline or satellite. The alternatecommunication path can provide the content server an option to continueservice delivery to the UE and maintain the SLA.

Further, a notification component 408 can be utilized to transmitrecommendation data (e.g., determined bandwidth availability, updates tocontent delivery parameters, alternate routing information, etc.) to acontent server. According to an embodiment, the notification component408 can transmit the recommendation data via in-band and/or out-of-band(e.g., satellite links) communication (e.g., to support disasterrecovery). As an example, a TCP header segment's 16-bit window sizefield (e.g., that is typically utilized to provide a size of the receivewindow) can comprise the recommendation data. The content server canthen perform the action based the information conveyed in the TCPheader. For example, the content server can adjust the data transmissionto the user device to maintain the defined QoS associated with thecontent delivery session or can utilize the alternate route to continuethe content delivery to conform the SLA.

Referring now to FIG. 5, there illustrated is an example system 500 thatemploys an artificial intelligence (AI) component 502 to facilitateautomating one or more features in accordance with the subjectembodiments. It can be noted that the OSS server 106, data collectioncomponent 402, analysis component 404, route determination component406, and notification component 408 can comprise functionality as morefully described herein, for example, as described above with regard tosystems 100-400.

In an example embodiment, system 500 (e.g., in connection withpredicting bandwidth availability, recommended actions to optimizecontent delivery, an alternate route for content delivery, etc.) canemploy various AI-based schemes (e.g., intelligent processing/analysis,machine learning, etc.) for carrying out various aspects thereof. Forexample, a process for determining which functions to monitor,determining requirements for a service, determining how to process rawdata, determining criterion and/or thresholds for scaling, etc., can befacilitated via an automatic classifier system implemented by AIcomponent 502.

Moreover, the AI component 502 can exploit various artificialintelligence (AI) methods or machine learning methods. Artificialintelligence techniques can typically apply advanced mathematicalalgorithms—e.g., decision trees, neural networks, regression analysis,principal component analysis (PCA) for feature and pattern extraction,cluster analysis, genetic algorithm, or reinforced learning—to a dataset. In particular, AI component 502 can employ one of numerousmethodologies for learning from data and then drawing inferences fromthe models so constructed. For example, Hidden Markov Models (HMMs) andrelated prototypical dependency models can be employed. Generalprobabilistic graphical models, such as Dempster-Shafer networks andBayesian networks like those created by structure search using aBayesian model score or approximation can also be utilized. In addition,linear classifiers, such as support vector machines (SVMs), non-linearclassifiers like methods referred to as “neural network” methodologies,fuzzy logic methodologies can also be employed.

As will be readily appreciated from the subject specification, anexample embodiment can employ classifiers that are explicitly trained(e.g., via a generic training data) as well as implicitly trained (e.g.,via observing device/operator preferences, historical information,receiving extrinsic information, type of service, type of device, etc.).For example, SVMs can be configured via a learning or training phasewithin a classifier constructor and feature selection module. Thus, theclassifier(s) of AI component 502 can be used to automatically learn andperform a number of functions, comprising but not limited to determiningaccording to a predetermined criterion, the bandwidth availabilityduring a defined time period, updates to data transmission parameters, acommunication path for optimized content delivery, etc. The criteria cancomprise, but is not limited to, historical patterns and/or trends,network operator preferences and/or policies, content/service providerpreferences, predicted traffic flows, event data, latency data,reliability/availability data, current time/date, servicerequirements/characteristics, real-time resource consumption, UEcharacteristics, UE category, UE behavior and/or motion data, type ofcontent, and the like.

FIGS. 6-8 illustrate flow diagrams and/or methods in accordance with thedisclosed subject matter. For simplicity of explanation, the flowdiagrams and/or methods are depicted and described as a series of acts.It is to be understood and noted that the various embodiments are notlimited by the acts illustrated and/or by the order of acts, for exampleacts can occur in various orders and/or concurrently, and with otheracts not presented and described herein. Furthermore, not allillustrated acts may be required to implement the flow diagrams and/ormethods in accordance with the disclosed subject matter. In addition,those skilled in the art will understand and note that the methods couldalternatively be represented as a series of interrelated states via astate diagram or events. Additionally, it should be further noted thatthe methods disclosed hereinafter and throughout this specification arecapable of being stored on an article of manufacture to facilitatetransporting and transferring such methods to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device orcomputer-readable storage/communications media.

Referring now to FIG. 6 there illustrated is an example method 600 thatfacilitates adjustment of a data transmission from a content serverbased on throughput availability that is conveyed to the content servervia in-band and/or out-of-band signaling, according to an aspect of thesubject disclosure. In an aspect, method 600 can be implemented by oneor more network devices (e.g., OSS server 106) of a communicationnetwork (e.g., mobility network). At 602, RAN analytics data can bereceived from one or more MEC servers via in-band and/or out-of-bandsignaling. As an example, the RAN analytics data can comprise, but isnot limited to RAN health, QoS, bandwidth utilization and/oravailability, capacity, throughput, etc. associated with the radiodownlink interface for a UE. In an aspect, the RAN analytics data can bereceived via a 16-bit window size field (e.g., reserved for indicating asize of the receive window) of the TCP header that is typically utilizedfor flow control data. Moreover, the RAN analytics data can be receivedvia in-band and/or out-of-band (e.g., satellite) communication and canthus support disaster recovery logic.

At 604, based on an analysis of the received data, a throughput that islikely to be available at the radio downlink interface (e.g., during adefined time period) can be determined. As an example, determination canbe facilitated via machine learning. In one aspect, the throughput canbe utilized to determine changes that are to be made to datatransmission of a content delivery session to, for example, improve theQoS/QoE. Further, at 606, the determined data (e.g., throughput and/orchanges) can be transmitted to a content server via in-band and/orout-of-band (e.g., satellite) communication to facilitate the adjustmentof one or more data transmission parameters, for example, to maintain adefined quality criterion. As an example, the determined data can betransmitted to the content server via a 16-bit window size field (e.g.,reserved for indicating a size of the receive window) of the TCP headerthat is typically utilized for flow control data.

FIG. 7 illustrates an example method 700 for determining alternateroutes for content delivery, according to an aspect of the subjectdisclosure. In an aspect, method 700 can be implemented by one or morenetwork devices (e.g., OSS server 106) of a communication network (e.g.,mobility network). At 702, RAN analytics data can be received from oneor more MEC servers via in-band and/or out-of-band signaling. As anexample, the RAN analytics data can comprise, but is not limited to RANhealth, QoS, bandwidth utilization and/or availability, capacity,throughput, etc. associated with the radio downlink interface for a UE.In an aspect, the RAN analytics data can be received via a 16-bit windowsize field (e.g., reserved for indicating a size of the receive window)of the TCP header that is typically utilized for flow control data.Moreover, the RAN analytics data can be received via in-band and/orout-of-band (e.g., satellite) communication and can thus supportdisaster recovery logic.

At 704, based on an analysis of the received data, a throughput that islikely to be available at the radio downlink interface (e.g., during adefined time period) can be determined. As an example, determination canbe facilitated via machine learning. Further, at 706, it can bedetermined whether the throughput satisfies a defined throughputcriterion (e.g., if the throughput is greater than a minimum throughputrequired for content delivery with a defined QoS). If determined thatthe throughput satisfies the defined throughput criterion, then at 708,content delivery can be performed via the current data transmissionroute/path. Alternatively, if determined that the throughput does notsatisfy the defined throughput criterion, then at 710, an alternateroute that is available for content delivery (e.g., having a throughputthat satisfies the throughput criterion) can be determined. In oneexample, the alternate route can utilize different communicationtechnologies than the current data transmission path. At 712, a contentserver can be notified regarding the alternate route via in-band and/orout-of-band (e.g., satellite) communication, for example, to enableservice continuity in accordance with a SLA. As an example, thealternate route data can be transmitted to the content server via the16-bit window size field (e.g., reserved for indicating a size of thereceive window) of the TCP header that is typically utilized for flowcontrol data.

Aspects and embodiments disclosed herein can be implemented in nextgeneration networks, for example, 5G networks. The 5G networkarchitecture is defined as service-based and the interaction betweennetwork functions can be represented as shown in FIGS. 8-9. FIG. 8illustrates an example system 800 that depicts a service-based networkarchitecture, according to an aspect of the subject disclosure. In anaspect, system 800 depicts service-based interfaces being used withinthe control plane. For example, one network function (NF) (e.g. accessand mobility management function (AMF) 816) within the control plane canallows other NFs (e.g., network slice selection function (NSSF) 802,network exposure function (NEF) 804, network repository function (NRF)806, policy control function (PCF), 808, user data management (UDM) 810,application function (AF) 812, authentication server function (AUSF)814, session management function (SMF) 818, user plane function (UPF)824, etc.) that have been authorized, to access its services. Thisrepresentation also includes point-to-point reference points between theNFs where necessary (e.g., between AMF 816 and UE, 820/(R)AN 822, SMF818 and UPF 824, (R)AN 822 and UPF 824, UPF 824 and data network (DN)826).

In an aspect, the AMF 816 can support termination of non-access stratum(NAS) signaling, NAS ciphering and integrity protection, registrationmanagement, connection management, mobility management, accessauthentication and authorization, security context management, etc. TheSMF 818 can support session management (e.g., session establishment,modification, release, etc.), UE IP address allocation and management,dynamic host configuration protocol (DHCP) functions, termination of NASsignaling related to session management, downlink (DL) datanotification, traffic steering configuration for UPF 824 for propertraffic routing, etc. Further, the UPF 824 can support packet routingand forwarding, packet inspection, QoS handling, can act as externalprotocol data unit (PDU) session point of interconnect to DN 826, andcan be anchor point for intra- and inter-radio access technology (RAT)mobility. A PCF 808 can support unified policy framework, provide policyrules to control plane functions, access subscription information forpolicy decisions in a unified data repository (UDR), etc. Additionally,the AUSF 814 can comprise an authentication server that authenticates UE820.

In an aspect, the UDM 810 can support generation of authentication andkey agreement (AKA) credentials, user identification handling, accessauthorization, subscription management, etc. The AF 812 can supportapplication influence on traffic routing, accessing NEF 804, interactionwith policy framework for policy control, etc. Further, the NEF 804 cansupport exposure of capabilities and events, secure provision ofinformation from external application to 3GPP network, translation ofinternal/external information, etc. Furthermore, the NRF 806 can supportservice discovery function, maintains NF profile and available NFinstances, etc. According to an embodiment, the NSSF 802 can supportselecting of the network slice instances to serve the UE 820 thatregisters via (radio) access network ((R)AN) 822, determining theallowed network slice selection assistance information (NSSAI),determining the AMF (e.g., AMF 816) set to be used to serve the UE, etc.

FIG. 9 illustrates an example system 900 that depicts a non-roaming 5Gsystem architecture in reference point representation, according to anaspect of the subject disclosure. In one aspect, system 900 focuses onthe interactions between pairs of network functions defined bypoint-to-point reference point (e.g. N7) between any two networkfunctions. This kind of representation is used when some interactionexists between any two network functions. It is noted that NSSF 802,PCF, 808, UDM 810, AF 812, AUSF 814, AMF 816, SMF 818, UE 820, (R)AN822, UPF 824, and DN 826, can comprise functionality as more fullydescribed herein, for example, as described above with regard to system800. It should be noted that although various aspects and embodimentshave been described herein in the context of 5G networks, the disclosedaspects are not limited to 5G technology and can be applied to otherfuture wireless communication technologies and their evolutions.

Referring now to FIG. 10, there is illustrated a block diagram of acomputer 1002 operable to execute the disclosed communicationarchitecture. In order to provide additional context for various aspectsof the disclosed subject matter, FIG. 10 and the following discussionare intended to provide a brief, general description of a suitablecomputing environment 1000 in which the various aspects of thespecification can be implemented. While the specification has beendescribed above in the general context of computer-executableinstructions that can run on one or more computers, those skilled in theart will recognize that the specification also can be implemented incombination with other program modules and/or as a combination ofhardware and software.

Generally, program modules comprise routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will note thatthe inventive methods can be practiced with other computer systemconfigurations, comprising single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the specification can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disk (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or other tangible and/ornon-transitory media which can be used to store desired information.Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and comprises any informationdelivery or transport media. The term “modulated data signal” or signalsrefers to a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediacomprise wired media, such as a wired network or direct-wiredconnection, and wireless media such as acoustic, radio frequency (RF),infrared and other wireless media.

With reference again to FIG. 10, the example environment 1000 forimplementing various aspects of the specification comprises a computer1002, the computer 1002 comprising a processing unit 1004, a systemmemory 1006 and a system bus 1008. As an example, the component(s),application(s) server(s), equipment, system(s), interface(s),gateway(s), controller(s), node(s), entity(ies), function(s), point(s),cloud(s) and/or device(s) (e.g., MEC servers 102, RAN analyticscomponent 104, OSS server 106, content server(s) 108, MEC server 202,edge cloud 204, UE 206, access point 208, core cloud 210, satellite 302,data collection component 402, analysis component 404, routedetermination component 406, notification component 408, AI component502, NSSF 802, NEF 804, NRF 806, PCF, 808, UDM 810, AF 812, AUSF 814,AMF 816, SMF 818, UE 820, (R)AN 822, UPF 824, and DN 826, etc.)disclosed herein with respect to systems 100-5 and 800-900 can eachcomprise at least a portion of the computer 1002. The system bus 1008couples system components comprising, but not limited to, the systemmemory 1006 to the processing unit 1004. The processing unit 1004 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 1004.

The system bus 1008 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1006comprises read-only memory (ROM) 1010 and random access memory (RAM)1012. A basic input/output system (BIOS) is stored in a non-volatilememory 1010 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1002, such as during startup. The RAM 1012 can also comprise ahigh-speed RAM such as static RAM for caching data.

The computer 1002 further comprises an internal hard disk drive (HDD)1014, which internal hard disk drive 1014 can also be configured forexternal use in a suitable chassis (not shown), a magnetic floppy diskdrive (FDD) 1016, (e.g., to read from or write to a removable diskette1018) and an optical disk drive 1020, (e.g., reading a CD-ROM disk 1022or, to read from or write to other high capacity optical media such asthe DVD). The hard disk drive 1014, magnetic disk drive 1016 and opticaldisk drive 1020 can be connected to the system bus 1008 by a hard diskdrive interface 1024, a magnetic disk drive interface 1026 and anoptical drive interface 1028, respectively. The interface 1024 forexternal drive implementations comprises at least one or both ofUniversal Serial Bus (USB) and IEEE 1394 interface technologies. Otherexternal drive connection technologies are within contemplation of thesubject disclosure.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1002, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to a HDD, a removable magnetic diskette, and a removableoptical media such as a CD or DVD, it should be noted by those skilledin the art that other types of storage media which are readable by acomputer, such as zip drives, magnetic cassettes, flash memory cards,solid-state disks (SSD), cartridges, and the like, can also be used inthe example operating environment, and further, that any such storagemedia can contain computer-executable instructions for performing themethods of the specification.

A number of program modules can be stored in the drives and RAM 1012,comprising an operating system 1030, one or more application programs1032, other program modules 1034 and program data 1036. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1012. It is noted that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1002 throughone or more wired/wireless input devices, e.g., a keyboard 1038 and/or apointing device, such as a mouse 1040 or a touchscreen or touchpad (notillustrated). These and other input devices are often connected to theprocessing unit 1004 through an input device interface 1042 that iscoupled to the system bus 1008, but can be connected by otherinterfaces, such as a parallel port, an IEEE 1394 serial port, a gameport, a USB port, an infrared (IR) interface, etc. A monitor 1044 orother type of display device is also connected to the system bus 1008via an interface, such as a video adapter 1046.

The computer 1002 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1048. The remotecomputer(s) 1048 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallycomprises many or all of the elements described relative to the computer1002, although, for purposes of brevity, only a memory/storage device1050 is illustrated. The logical connections depicted comprisewired/wireless connectivity to a local area network (LAN) 1052 and/orlarger networks, e.g., a wide area network (WAN) 1054. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1002 isconnected to the local network 1052 through a wired and/or wirelesscommunication network interface or adapter 1056. The adapter 1056 canfacilitate wired or wireless communication to the LAN 1052, which canalso comprise a wireless access point disposed thereon for communicatingwith the wireless adapter 1056.

When used in a WAN networking environment, the computer 1002 cancomprise a modem 1058, or is connected to a communications server on theWAN 1054 or has other means for establishing communications over the WAN1054, such as by way of the Internet. The modem 1058, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1008 via the serial port interface 1042. In a networkedenvironment, program modules depicted relative to the computer 1002, orportions thereof, can be stored in the remote memory/storage device1050. It will be noted that the network connections shown are exampleand other means of establishing a communications link between thecomputers can be used.

The computer 1002 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g.,desktop and/or portable computer, server, communications satellite, etc.This comprises at least Wi-Fi and Bluetooth™ wireless technologies orother communication technologies. Thus, the communication can be apredefined structure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity networks use radio technologies called IEEE802.11 (a, b, g, n, etc.) to provide secure, reliable, fast wirelessconnectivity. A Wi-Fi network can be used to connect computers to eachother, to the Internet, and to wired networks (which use IEEE 802.3 orEthernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radiobands, at an 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, forexample, or with products that contain both bands (dual band), so thenetworks can provide real-world performance similar to the basic 10BaseTwired Ethernet networks used in many offices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “data store,” data storage,”“database,” “cache,” and substantially any other information storagecomponent relevant to operation and functionality of a component, referto “memory components,” or entities embodied in a “memory” or componentscomprising the memory. It will be noted that the memory components, orcomputer-readable storage media, described herein can be either volatilememory or nonvolatile memory, or can comprise both volatile andnonvolatile memory. By way of illustration, and not limitation,nonvolatile memory can comprise read only memory (ROM), programmable ROM(PROM), electrically programmable ROM (EPROM), electrically erasable ROM(EEPROM), or flash memory. Volatile memory can comprise random accessmemory (RAM), which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such assynchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM),double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), SynchlinkDRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, thedisclosed memory components of systems or methods herein are intended tocomprise, without being limited to comprising, these and any othersuitable types of memory.

Referring now to FIG. 11, there is illustrated a schematic block diagramof a computing environment 1100 in accordance with the subjectspecification. The system 1100 comprises one or more client(s) 1102. Theclient(s) 1102 can be hardware and/or software (e.g., threads,processes, computing devices).

The system 1100 also comprises one or more server(s) 1104. The server(s)1104 can also be hardware and/or software (e.g., threads, processes,computing devices). The servers 1104 can house threads to performtransformations by employing the specification, for example. Onepossible communication between a client 1102 and a server 1104 can be inthe form of a data packet adapted to be transmitted between two or morecomputer processes. The data packet may comprise a cookie and/orassociated contextual information, for example. The system 1100comprises a communication framework 1106 (e.g., a global communicationnetwork such as the Internet, cellular network, etc.) that can beemployed to facilitate communications between the client(s) 1102 and theserver(s) 1104.

Communications can be facilitated via a wired (comprising optical fiber)and/or wireless technology. The client(s) 1102 are operatively connectedto one or more client data store(s) 1108 that can be employed to storeinformation local to the client(s) 1102 (e.g., cookie(s) and/orassociated contextual information). Similarly, the server(s) 1104 areoperatively connected to one or more server data store(s) 1110 that canbe employed to store information local to the servers 1104.

What has been described above comprises examples of the presentspecification. It is, of course, not possible to describe everyconceivable combination of components or methods for purposes ofdescribing the present specification, but one of ordinary skill in theart may recognize that many further combinations and permutations of thepresent specification are possible. Accordingly, the presentspecification is intended to embrace all such alterations, modificationsand variations that fall within the spirit and scope of the appendedclaims. Furthermore, to the extent that the term “comprises” is used ineither the detailed description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receiving,from a mobile edge computing device, analytics data associated with aradio access network serving a user equipment; based on an analysis ofthe analytics data, estimating throughput data indicative of anavailable throughput of a radio downlink interface employable to delivercontent to the user equipment; in response to determining that thethroughput data satisfies a low throughput criterion, determining routedata indicative of an alternate route for delivery of the content to theuser equipment; and facilitating, via out-of-band signaling, atransmission of the route data to a content server that provides thecontent, wherein the alternate route is employable by the content serverto transfer the content in accordance with a service level agreement. 2.The system of claim 1, wherein the receiving comprises receiving theanalytics data via out-of-band signaling.
 3. The system of claim 1,wherein the analytics data is received within a window size field of atransmission control protocol header segment that has been reserved forindicating a size of a receive window of time.
 4. The system of claim 1,wherein the facilitating comprises facilitating the transmission of theroute data within a window size field of a transmission control protocolheader segment that has been reserved for indicating a size of a receivewindow of time.
 5. The system of claim 1, wherein the analytics datacomprises to quality of service data.
 6. The system of claim 1, whereinthe analytics data comprises a performance parameter associated with thedelivery of the content.
 7. The system of claim 1, wherein theoperations further comprise: storing information indicative ofrespective bandwidth availabilities associated with alternate routesthat are employable to deliver the content from the content server tothe user equipment, and wherein the alternate route is selected from thealternate routes based on the information.
 8. The system of claim 1,wherein the content comprises video data associated with a videostreaming service.
 9. The system of claim 1, wherein the alternate routecomprises a route that utilizes satellite communication.
 10. A method,comprising: determining, by a system comprising a processor, analyticsdata associated with a radio access network serving a user equipment,wherein the determining comprises receiving the analytics data from amobile edge computing device, based on an analysis of the analyticsdata, determining, by the system, throughput data indicative ofthroughput of a radio downlink interface that is likely to be availableduring a defined time period according to a defined likelihoodcriterion, wherein the radio downlink interface is associated with theradio access network and is employable to deliver content to the userequipment; in response to determining that the throughput data satisfiesa low throughput criterion, determining, by the system, route dataindicative of an alternate route for delivery of the content to the userequipment; and facilitating, by the system, a transmission of the routedata to a content server that provides the content via out-of-bandsignaling, wherein the alternate route is employable by the contentserver to transfer the content in accordance with a service levelagreement.
 11. The method of claim 10, wherein the receiving comprisesreceiving the analytics data from the mobile edge computing device viaout-of-band signaling.
 12. The method of claim 10, wherein the receivingcomprises receiving the analytics data from the mobile edge computingdevice via a window size field of a transmission control protocol headersegment that has been reserved for indicating a size of a receivewindow.
 13. The method of claim 10, wherein the facilitating thetransmission comprises facilitating the transmission of the route datavia a window size field of a transmission control protocol headersegment that has been reserved for indicating a size of a receivewindow.
 14. The method of claim 10, further comprising: based on thethroughput data, determining, by the system, modification dataindicative of an updated data transmission parameter that improves aquality associated with the delivery of the content.
 15. The method ofclaim 10, wherein the receiving the analytics data comprises receivinginformation relating of a health status of the radio access network. 16.The method of claim 10, further comprising: instructing, by the system,the mobile edge computing device to initiate measurements that areemployed to determine the analytics data.
 17. A non-transitorymachine-readable medium, comprising executable instructions that, whenexecuted by a processor, facilitate performance of operations,comprising: receiving analytics data associated with a radio accessnetwork serving a user equipment, wherein the analytics data isdetermined via a mobile edge computing device, analyzing the analyticsdata to determine throughput data indicative of throughput of a radiodownlink interface that is likely to be available during a defined timeperiod, wherein the radio downlink interface is associated with theradio access network and is employable to deliver content to the userequipment; in response to determining that the throughput data satisfiesa low throughput criterion, determining route data indicative of analternate route for delivery of the content to the user equipment; andfacilitating, via out-of-band signaling, a transmission of the routedata to a content server that provides the content, wherein thealternate route is employable by the content server to transfer thecontent to satisfy a criterion specified within a service levelagreement.
 18. The non-transitory machine-readable medium of claim 17,wherein the receiving comprises receiving the analytics data from themobile edge computing device via out-of-band signaling.
 19. Thenon-transitory machine-readable medium of claim 17, wherein thereceiving comprises receiving a transmission control protocol headersegment that comprises a window size field that has been reserved forindication of a size of a receive window, and wherein the window sizefield comprises the analytics data.
 20. The non-transitorymachine-readable medium of claim 17, wherein the facilitating thetransmission comprises directing, to the content server, a transmissioncontrol protocol header segment that comprises a window size field thathas been reserved for indication of a size of a receive window, andwherein the window size field comprises the route data.